Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-206678 | SRG-NET-000074-FW-000009 | SV-206678r604133_rule | Medium |
Description |
---|
Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit event content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the network element logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network element. |
STIG | Date |
---|---|
Firewall Security Requirements Guide | 2024-05-28 |
Check Text ( C-6935r297813_chk ) |
---|
Examine the traffic log configuration on the firewall or view several alert events on the organization's central audit server. Verify the entries sent to the traffic log include sufficient information to determine the type or category for each event in the traffic log. If the traffic log entries do not include enough information to determine what type of event occurred, this is a finding. |
Fix Text (F-6935r297814_fix) |
---|
Configure the firewall to ensure entries sent to the traffic log include sufficient information to determine the type or category for each event in the traffic log. |